Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[vRNI-NI] [4.x] FAQ - Integration with VMC (65112)

Last Updated: 1/21/2019Categories: InformationalTotal Views: 3009Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

The purpose of this article is to provide guidance and general information on the VMware on Cloud for AWS (VMC) integration with vRealize Network Insight 4.x / Network Insight 4.x

Resolution

What is vRealize Network Insight?

VMware vRealize Network Insight delivers intelligent operations for software-defined networking and security. It helps customers build an optimized, highly-available, and secure network infrastructure across multi-cloud environments. It accelerates micro-segmentation planning and deployment, enables visibility across virtual and physical networks, and provides operational views to manage and scale VMware NSX deployments.

More information is available at https://docs.vmware.com/en/VMware-vRealize-Network-Insight/index.html

What is Network Insight?

VMware Network Insight is a VMware Cloud Service that offers the same capabilities as vRealize Network Insight. It provides visibility into the networking and security flows of your on-premises and cloud applications as well as into monitoring your NSX-based SDDC.

More information is available at https://docs.vmware.com/en/VMware-Network-Insight/index.html

How do I sign up for Network Insight service?

When you sign up for a VMware Cloud service, or when someone invites you to join a service, you receive an email invitation containing a link that you use to sign up.

You sign up for VMware Cloud services with your VMware ID. If you do not have a Customer Connect account, you create one as you sign up.

Procedure:

Click the link in your invitation mail.

Sign up for VMware Cloud:

If you have a VMware ID, follow the steps to sign up to VMware Cloud with your VMware ID credentials.

If you do not have a VMware ID, follow the steps to create your Customer Connect account, and sign up to VMware Cloud.

Log in to VMware Cloud with your VMware ID. If you are not redirected to the VMware Network Insight page, go to https://www.mgmt.cloud.vmware.com/.

Which all outgoing traffic require access through the firewall?

HTTPS port 443 open to outgoing traffic with access through the firewall to:

*.vmwareidentity.com

gaz.csp-vidm-prod.com

*.vmware.com

*.ni-onsaas.com

Note: Due to images size limitation with the system, we suggest you to open the images in new tabs, zoom in the browser or download the below screenshots for a better understanding of each step.

Any firewall rules to be created in customer environment?

Management Gateway Firewall rule to allow vRNI/NI collector to invoke NSX Manager APIs over HTTPS (443). A sample screenshot of the firewall rule is shown below:

Note: While the rule above specifies the “Source” in the firewall rule as Any; it is recommended that a more stricter criteria be specified for the “Source” so that only the collector VM can communicate with the proxy.

Compute gateway rule within the Gateway Firewall  to allow collector to communicate with the on-Prem Platform/NI.

Note: While the rule above specifies the “Source” in the firewall rule as Any; it is recommended that a more stricter criteria be specified for the “Source” so that only the collector VM can communicate with the proxy.

What should be roles/permission required for user adding VMC data sources?

For VMC VCenter:

CloudAdmin

For VMC NSX Manager:

CloudAdmin or CloudAuditor (read-only user)

Note: The user needs to have role of Cloud Admin in order to enable DFW IPFIX on VMC Policy Manger. A user with Cloud Auditor role has read-only privileges and would not be able to perform tasks like enable/disable DFWIPFIX.

Not able to get data due to wrong/mismatch configuration of NSX Manager and vCenter

If an incorrect VMC NSX Manager is configured with a VMC VCenter, then critical data required for Flows and Topology to function correctly would be missing. In such cases, the remediation would be to delete the incorrectly added VMC NSX Manager data source and add a new VMC NSX Manager data source using the correct VMC VCenter and NSX Manager.

Unable to enable DFW IPFIX ?

Depending on whether vRNI/NI can enable DFW IPFIX on Policy Manager with the given user there can be following error messages.

1) No new collectors can be added.

VMC Policy Manager allows only 4 collectors to be added to its DFW IPFIX Collector Profile. This error will be seen when the existing DFW IPFIX Collector Profile already has 4 collectors added to it.

2) Provided user does not have the required role. Only users with the following role can enable IPFIX:  Cloud Administrator.

Only the above-mentioned roles in VMC can do a write operation on VMC Policy Manager. As while enabling DFW IPFIX on Policy Manger we need to add/update the DFW IPFIX Profile or DFW IPFIX Collector Profiles on Policy Manger we need the user to have write permissions.

How to obtain CSP refresh token for NSX Manager?

Step 1:  Login to your VMWare Cloud Services console

Step 2: Click on VMWare Cloud on AWS in My Services.

Step 3: Click on the desired SDDC name.

Step 4: Click on Support Tab. Note the NSX Manager IP shown in the page.

Step 5: Click on the  present at the top right corner of the screen.

Step 6: Now click on API Tokens Tab and copy the Refresh Token. Refresh token have a lifetime of 6 months and their lifecycle tracking is outside the scope of vRNI/NI

How to obtain credentials for VCenter?

Step 1:  Login to your VMWare Cloud Services console

Step 2: Click on VMWare Cloud on AWS in My Services.

Step 3: Click on the desired SDDC name.

Step 4: Click on Settings Tab

Step 5: Click on the vCenter FQDN to get the VCenter FQDN. Click on Default vCenter User account to find the User Name and Password. Click on the  icon to copy the Password / User Name to clipboard. Note the FQDN, Username and Password. These will be required to add the data source in vRNI/NI.

Related Information

For guidance and general information on the VMware on Cloud for AWS (VMC) integration as a data source for vRealize Network Insight 4.x, see the following kb :
https://kb.vmware.com/s/article/65100

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Certificate Manager 替换证书在 0% 时失败： 操作失败，正在执行自动回滚 (2111571)

KB
•
Horizon 7 コンポーネントの PCoIP セキュリティ プロトコルと暗号スイートの設定 (2130798)

KB
•
vmware.log 文件中显示“File system specific implementation of LookupAndOpen [file] failed” (2149438)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Network Insight

Related Versions:

Take Our Survey

Support Assistant